Issue #30: As a Devops, I would like to rework the file structure in this directory #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request revamps the repository's folder structure, ensuring alignment with industry best practices and enhancing clarity based on our specific requirements. We want to adopt best practices according to our goal of replicating the infrastructure across various environments hosted in separate accounts.
For Terraform, in line with our vision of multi-environment infrastructure, we have adopted a structure endorsed by this guide which is designed for manageability across different environments with different accounts:
In the case of Kubernetes, we are consolidating all Kubernetes manifests within a single monorepo, following the structure recommended by this guide. This structure is similar to a project Thomas and me have previously worked on) :
For our current needs, the current folder structure for Kubernetes is enough and no modifications are currently needed.